RoleScreen

Description

This business rule allows for the configuration of the Role screen and defines the dynamic fields that can be displayed and updated on the specified Role Detail(s) screens.  The plan selected during the policy entry process dictates which role options are visible and available on the Role screen. 

 RoleScreen Element/Attribute Table

Element/Tag

Definition

Attribute

Element/Attribute Value and Description

<RoleScreen>

The opening and closing tag for the business rule.

 

 

    <Role>

Required/Repeatable Element;
Parent element that has sub elements to hold required information or have available information for a specific role that is defined separately by this tag.

ROLECODE

Required Attribute;
RoleCode
To represent the role code (as defined in AsCodeRole) for which the information should be captured or made available for each role code.

       <Fields>

Allows configuration of dynamic fields.

 

 

    <SucessorOnDelete>

Optional element;
This element allows the system to replace one role with another upon deletion of the original role.

 

Required element value;
RoleCode
This is the role with which the original role should be replaced, upon its deletion.
 

Note: The original role's RoleCode is specified in the <Role> tag. If the new role does not exist, then the user is warned with the same.

DELETEOLDROLE

Yes:  Delete old role.

No:  Keep old role.

IGNOREONSTATUS

StatusCode

Do not replace role if it is in the status identified in the IgnoreOnStatus attribute.  

   <Events> 

See Action/Events.

 

 

 

RoleScreen Image 

OIPA Roles Screen

 

Database Tables for RoleScreen

Table Name

Description

AsAddress

Stores client address information.

AsAddressField

Contains address information organized by guaranteed user identification.

AsAddressRole

Contains address information organized by the role.

AsClient

Stores personal information about clients.

AsCode

Contains a listing and description of all valid codes and their values.

AsRole

Contains role information.

XML Example

<RoleScreen>

     <Role ROLECODE=”13”>

       <Fields>

          <Field>

             <Name>OverRideAddress1</Name>

             <Display>Override Address</Display>

             <DataType>Combo</DataType>

             <Query TYPE=”SQL”>SELECT &ldots;. </Query>

          </Field>

                    <Field>

             <Name>Line</Name>

             <Display></Display>

             <DataType>Line</DataType>

        </Field>

        <Field>

             <Name>Line</Name>

             <Display></Display>

             <DataType>Line</DataType>

        <Field>

        <Field>

             <Name>AlternateCorrespondence</Name>

             <Display>Correspondence to Alternate Address</Display>

             <DataType>Text</DataType>

        </Field>

        <Field>

             <Name>AlternateConfirmation</Name>

             <Display>Confirmations to Alternate Address</Display>

             <DataType>Text</DataType>

        </Field>

        <Field>

             <Name>AlternateStatements</Name>

             <Display>Statements to Alternate Address</Display>

              <DataType>Text</DataType>

         </Field>

      </Fields>

   </Role>

</RoleScreen>

 

Schema Example

<RoleScreen>

<Role ROLECODE="[CodeString]">

<Fields> </Fields>

<SuccessorOnDelete DELETETOLDROLE="[Yes|No]" IGNOREONSTATUS="[StatusCode]">[RoleCode]</SuccessorOnDelete>

</Role>

</RoleScreen>